WWWworkbench v 2.0
for AWeb-II 3.1+
by Andres Pääbo ©98
Introduction
PREFACE
This project developed as a result of my doing some commercial work creating websites with lots of graphics (see later for some of my websites). In the process of creating websites with a nice graphic appearance, it is necessary to view what you have visually. Thumbnail systems have the problem that you have to deliberately create the thumbnails. Also not all software support the same thumbnails (ie for loading and saving). Thirdly, if you move files, the thumbnails will not move with the file (except for newicons, and thumbnails that are actually put onto the workbench icons--but when thumbnails are put on workbench icons, the workbench slows down ...and so it goes....)
But for website work how necessary are permanent thumbnails anyway? Websites are designed to travel over phone lines, and most images used should be under 15k so as not to try the average internet user's patience. Website images arrive quickly. So they do not need thumbnails. They only need to be scaled to a fixed size and layed out on the screen for easy viewing. The HTML parameters of WIDTH= and LENGTH= for images, make browsers natural image scalers. So why not load all images, from their source, and generate a temporary html document with images required to be scaled to a specified WIDTH and HEIGHT.
It is relatively easy to do, and some others have done so.
But when I began doing so, I started running into real world problems and requirements. What is the file name? What is its filesize? How would you use browser displays of directory contents? What about non-images in the directories? What about directories? What about navigation? What can we do with the thumnail display when it is created? One answer led to another and another and eventually the result is WWWworkbench.
It is called this because in its final form it resembles a workbench. You open many browser windows each with thumbnail -size displays, and perform typical directory editing actions on them--just like regular workbench windows. Version 1.0 was a basic version originally designed for IBrowse 1.2. Because of limited IBrowse arexx commands, actions on files was all done by file requesters. This version for AWeb 3.1 is so much more advanced that it was necessary to jump the number. Using special arexx-supporting features in AWeb 3.1, especially the ability to not only launch an arexx script from a web page link but also to pass arguments to it , allowed almost unlimited potential. Now, in this AWeb version, instead of requesters, there is workbench-like operation. If you click a file thumbnail, you activate it for menu operations. If you double click a thumbnail you view the original; if you double click a drawer it opens up. And much more......
This is not a true program. It is a system of interrelated and interdependent scripts and html documents triggered by links on the browser display, and feeding the browser script-generated html documents. This is a first version of the complex v 2.0 form, so it will be fixed and improved as various problems crop up or if I can see more efficient ways of performing the operation internally or externally. I offer this as shareware because it is quite elaborate and took me much time (and I will inevitable spend more time on it). Whoever is registered, will get improvemetns and fixes and additional scripts via email.
HOW CREATED
Programmers tend to design a computer program from the point of view of acheiving a very fast and efficient script that does many things. But the interface and operations may not be as good as when the project starts with the interface, and works backwards. The interent browser is by its very nature an interface creator. So you can easily envision how the interface should look, nd then work backwards to determine what should happen underneatht to generate the html code that will rpoduce the desired effect. I'm not a programmer, but come from the real world of art; so my prime interest is the interface and operation. Making the operation and interface the greater importance may result in less efficient operations underneath, but the way I look at it its that if the arexx script takes a second longer to do something, and if it looks untidy in form, what does it matter? WWWworkbench was built up interractively. First you get something happening and then add and change this and that. It becomes more and more complex and messy; but when it is running properly it can be rewritten, tightened up, after turning attention to the script operation as opposed to the user interface. The objective is to get the final operation first, and then to tighten up the scripts afterward. The above approach, of building it interractively as you go, can result in scripts that even the creator cannot understand mere hours later. At one point I put this aside for two weeks. When I came back, to make changes, it took me two hours of studying it, before I could begin. I considered subtitling WWWworkbench as 'An experiment in how complicated you can get with use of arexx scripts'
FEATURES
- APPLICABILITY TO DESIGN OF WEBSITES
Because of its applicability to internet use, I thought, why not call it WWWworkbench. The "WWW"coming from "World Wide Web". Although created to help in designing websites locally, (websites are normally designed locally and then uploaded), I added support for FTPMount ©Evan Scott, available on aminet, mainly because FTPMount simulates remote directories on the workbench, and therefore the same operations used on local directories should work on it okay. I discovered that the browser cannot load files via FTPMount, so the system uss FTPMount for directory management, and the actual viewing by the browser ius achieved via http: to the same directory. Thus you must have both FTP and HTTP access to the same directory. Through the use of FTPMount, WWWworkbench can include the remote website as well. For example you can copy local files into the remote directory (ie upload). Thus making useage for website design complete. WWWw does not need FTPMount, but if you have it installed and configure WWWw for it, you can use it. For more on FTPMount, look for it on the aminet. (There is a recent upgrade, but I found the upgrade failed on one of my websites, so if the upgraded version fails, check the original too)
- WORKBENCHLIKE OPERATION
WWWworkbench displays the
contents of directories in graphic manner, with browser
windows acting like workbench windows. As many browser windows can be
opened as desired, and, if the navigation buttons, etc are
removed, it actually has a workbench-like character. The
graphic display of the directories are based on the inbuilt
abilities of the browser to view files, both internally and with
external viewers. Those images that can be scaled are scaled
to thumbnail size. Other files are shown as boxes.
- LINKS LAUNCH AREXX SCRIPTS
Through
the inbuilt support for launching arexx scripts available in AWeb-II 3.1, links in the
html pages are used to trigger arexx scripts which send
Amigados commands for editing (delete, copy, clone, etc). If
you have FTPMount, the editing capabilities are extended to
remote directories.
- IDEAL FOR WEBSITE DESIGN
WWWworkbench is ideally used for work in website design. In website design , many kinds of graphic elements are brought together, orchestrated; and in order to do it well the designer needs to be able to have a good overview of all resources starting with the graphics. WWWworkbench displays the content of entire directories--website directories being developed locally before being uploaded-- in as many windows as you want to open. It also allows you the ability to copy, files between directories, delete, move, clone, etc..
- DESIGNED FOR IBROWSE 1.2 (WWWw version 1.0) AND AWEB-II 3.1 (WWWw version 2.0)
(WWWworkbench 1.0 only exists for IBrowse 1.2 --see WWWworkbenchIB.lha on aminet. It works, but lacks frills. You can select files via file requester. The limitations are on account of the shortage of arexx commands in IBrowse 1.2. ) This veersion you are looking at, WWWworkbench 2.0 exists for AWeb-II 3.1 . It is so much more complex than v 1.0, on acocunt of its using AWeb arexx support to the full, that it has to be called version 2.0. An IBrowse version 2.0 would depend on whether the next IBrowse (2.0) provides enough of the arexx support needed to do the same things currently done in the AWeb version.
WHAT IT IS AND WHAT IT DOES
- A SYSTEM OF SCRIPTS
Although WWWworkbench looks and feels like a separate software, it is nothing more than a cleverly organized system of arexx scipts. Note that WWWworkbench is only hosted by the supported Amiga browser and all the possibilities built into the host browser are useable. All WWWworkbench does is use AmigaDos commands, orchestrated by Arexx scripts, to generate html docs on the fly, which the browser loads. The browser in addition can provide all the viewing, etc that you hve configured into the browser. Thus the browser is always dealing with html docs, urls, etc. and all the browser functions remain usable--viewing, downloading, delaying image loading, logging, caching, and so on. You can have TCP running and take a break and load a webpage if you like!
- A THUMBNAIL DOCUMENT GENERATOR
WWWworkbench generates the thumbnail docs on-the-fly and they are temporarily placed in a special drawer Ram:T/W4. Some files in there are not deleted as they may be reused, but the thumbnail docs are deleted after they are loaded. Some may find these thumbnail docs useful (you can build an archive-viewing website on a CD, for example). But you can still save these pages even if they are deleted in Ram:T/W4. after they appear on screen. To save them, just click the window you are interested in and save the thumbnail html script wherever you want. Just select Save-Source and save it.
AREXX SCRIPTS AND WWWw
It is important to note that unknown
arexx scripts are dangerous . That is why the AWeb folks havee designed their arexx support so that x-aweb:rexx/ will launch only local arexx scripts. By running an arexx script, you are allowing the creator of that script to operate your AmigaDos commands. (And this is also true of installation scripts when you install software--poor docs don't tell you what the installation script will do.) Anyway, the most dangerous thing would be if a bad, or evil arexx script deletes directories. (My suggestion is that before you run any unknown arexx script search it for the word ALL, because 'Delete ALL' will not ask your permission to delete a directory. Normally arexx scripts will delete only files that they created in Ram: or Ram:T ) . So for your information, here is what WWWworkbench does in terms of creating or deleting directories and files: It creates a temporary directory, Ram:T/W4 , and EVERYTHING WWWworkbench generates and/or deletes is put in there, with the following exception: to save a permanent configuration file ( W4-config.txt ) to the WWWworkbench directory. You can also SAVE a selection list, but you will be presented with a file requester so you can choose where it will go. The directory Ram:T/W4 will remain until you reboot or explicitly delete it. The few script files in RAM:T/W4 are so small in filesize that they barely take up any memory. If it is a problem for anyone, just open Ram: T and delete it.
I could put a 'close' button on the title page which does it, if many want it...
Installation & Configuration
INSTALLATION
1. USE INSTALL SCRIPT
The install script will copy the directory WWWworkbench to the Plugins directory of Aweb,
and you can select to add STARTWWWworkbench to the arexx menu
or other methods of launching WWWworkbench to AWeb. After
installation, find the menu or button you have created and launch it.
You can then test it and if desired further configure it.
2.MANUAL INSTALLATION
- 2a. After de-archiving the -'lha ' file you will find a directory
called WWWworkbench. To install, just copy (or drag on the
workbench) this drawer into AWeb's Plugins directory. This is the directory that contains directories of other arexx scripts like FTPlus, and is the desired location for such arexx support programs.
- 2b.Configure the supported Amiga browser to be able to launch WWWworkbench.
Go to the browser 'settings' menu (Aweb:Settings-GUIsettings-Arexx) and create an Arexx menu item for the browser's drop down arexx menu, so that you can launch
WWWworkbench from the menu. A good label would be
'START WWWworkbench'. You will also need to install the path to the appropriate file which is StartWWWWworkbench.awebrx. NO OTHER SCRIPTS NEED BE INSTALLED: All other arexx scripts are launched from links. If you like you can create GUI gadgets, or keyboard methods of launching WWWworkbench
- 2c.CONFIGURE THE BROWSER TO BE ABLE TO LAUNCH AREXX SCRIPTS: AWeb 3.1 automatically supports launching arexx scripts, so nothing has to be done. WWWworkbench for AWeb is written using 'x-aweb:rexx/' by which AWeb will launch arexx scripts.
- 2d.Select SAVE SETTINGS to save these changes (or they
will be lost when you exit)
- 2e.Select from the supported browser AREXX menu, the label you
installed (START WWWworkbench), to see the title page
load into the browser window. You are all set with default settings. The following configuration can be pursued in due time.
CONFIGURATION
- WINDOW SIZES AND POSITIONS:
In the ideal use of WWWworkbench , you want to open a number of windows that do not fill the entire screen so you can move them around as on a table (which is also the original concept of the workbench).
In WWWworkbench for AWeb, the opening window and the Guide window and View windows need to be user resized. You can exert some predicatable behaviour by 'snapshotting'. The most important windows, are, happily, automatically sized according to yoour selection if the size, and numberacross of the filethumbnails. You will notice that when drawers are opened they are sized according to the thumbnail configuration you have chosen, and pushed into the upper right corner. The upper left corner gets the 'selection list' window whose images are exactly half in size. Thus configuring window size is linked to other configurations below.
- FONTS:
For the file names, filesizes and dates to fit, you need the smallest size font you are comfortable with, otherwise you cannot make the thumbs very small. The generated html code uses FONT SIZE= 1 (ie -3, smallest) for the thumbnail pages. WWWworkbench has been designed with Times 11 as the smallest font. Note it is more important that the font be compact sideways--ei condensed-- rather than vertically. Another good choice: Universe 9 is about as small as you can get while still being readable. Both of these came with the Amiga. The filesize can affect the display in that your specifications of filethumbnail size will be overridden by space needed to write the text. The length of your filenames of course affects it too. So if you see a column with a great amount of space at sides, scroll down and you will probably find a long filename.
- LAYOUT:
WWWw is designed for an 800x600 minimum screen. New directory windows opn in the top right corner and the selection list in the top left. After a directory window appears at top right, drag it wherever you want. Obviously in this form of browser use, you do not need all the periferals for navigating the internet. Perhaps in future AWeb will be adjusted so that if it is used in a non-internet way, that the internet functions and gadgets can be removed. (Gadgets can be removed from AWeb but not in any instant and convenient way. )
- SCREEN:
WWWworkbench is designed for a 800x600 graphic card screen. If you have less, then I can't guarantee it will be as aesthetic to use.
- CONFIGURING THE THUMBNAIL DISPLAY
You can modify the width, height, spacing, and number of thumbnails across the page of the generated rectangles(thumbanils, etc). Recommended thumbnail sizes are 80x60, 100x90, 160x120 because they are in the ratio of common jpeg files (320x240m 640x480), so most images will not appear to be distorted. More important is your control of the filesize that the browser will load and scale to thumb size. If you have a large file among small ones, the generation of the display will get hung up with the time it takes to load the large file and scale it down. On the internet, web pages rarely have image and graphic files more than about 15 kilobytes. In WWWw the variable is called maxautosize. If you set it at 15, then the browser will load, if it can, all files under 15k, but offer a BIG FILE icon only if it exceeds. Your choice of the maxautosize will depend on computer speed. (and speed of phone line transmission if you are using FTPMount and the WWW.)If you are loading local files with an accelerated computer you might do fine with 200k. NOTE: the moment you hit the 'apply new values', the changes take effect. All open windows are refreshed to the new settings. If you like what you see, click 'Save Current Config Settings', which will write the file to WWWworkbench/W4config.txt and will be used the next tme you launch WWWworkbench.
- CONFIGURING FOR FTPMOUNT USE
While WWWworkbench was designed for viewing local directories, the clever system called FTPMount ©by Evan Scott and available from the Aminet , is utilized by WWWworkbench to allow you to manipulate your website , by the FTPMount system of making remote directories appear as workbench directories and files, which are operated by regular Amigados commands (delete, rename, copy, etc.). Because WWWworkbench needs to operate differently with FTPMount files than with regular local files, some configuring is needed. You will find FTPMount configure fields at the bottom of the title page (scroll down). What you have to do is to provide both the FTPMount address and the HTTP address TO THE SAME PLACE. Do not enter quote marks. Make sure you do not add invisible spaces at front or back. To ensure no invisible blanks, hit return right after entering the last character in the address. (Basically, extra blanks screw up the parsing of the entry). To check if all is fine, look at the W4config.txt file that is created.
Useage
GENERAL
The concept here is that you have several windows open at the same time, reduced from screen size so you can view two or three directories at the same time. You can then perform operations between them--copy or move pictures from one directory to another, delete this or that, rename for greater clarity... A good approach for such operations is to place two vertical half-screens side by side , dividing the screen in two. Set the number of pictures in a row to about three or four (depending on how small the thumbnails.). Since changes are immediate you can change the thumbnail size, number across, and the maximum filesize allowable to be loaded to thumbnail--ANYTIME.
WWWworkbench operates very much like a workbench--if you click a thumbnail you select it, and when you double click you open it up (drawer) or view it (file). But it goes far beyond workbench operations in that a central feature is that you can assemble a selection of images into the Selection List (and these selections can come from many directories). Operations can then be performed on the files in the selection list, including passing the selected files to another open program, like ImageFX or Personal Paint
The following is an inventory of specific things you can do:
VIEWER OF CONTENTS OF DIRECTORIES
- DISPLAY OF CONTENTS OF DIRECTORY
On every display there is a drawer icon at the top. When you click it, you get a file requester. You can open a new drawer window with it, or directly view a file. When you select any DRAWER icon, other than the one at the top, you can perform actions on it if scripts are written for it. .If you click twice in a row on the drawer icon, the drawer will open up a new window with its contents.
- VIEW A FILE OR SEVERAL:
A file can be viewed three ways: 1. Directly choose it from a file requester. 2.If you click a file icon or thumbnail twice in a row, it will activate a VIEW of that file. 3.If you select several files, then use the VIEW menu item--it will open as many windows as selected files.
If the selected item is a drawer, then operations can be done on the selected drawer, and if the drawer is double-clicked, it will open up.
- MENU ACTION ON A FILE OR SEVERAL:
There are two modes--the single selection mode and the multiple select mode. For convenience I have put the notes for this in W4guidenotes.html which automatically appears in a window on the title page. Also, it is discussed below in the section MENU OPERATIONS. Briefly, if you click a single image, no selection list will appear, and you can select action menu items immediately. But the moment you select a second image, a selection list is created. Existing selectionlists are preserved, even if not visible, until you CLEAR it. You can close a selection list window (to get it out of he way) with the close button, but see it again by selecting the 'SL' link (to the left of the top drawer icon in the drawer window)
INFORMATION ABOUT THE FILES:
- BIG FILES:
You also configured the maximum filesize that the browser will load so that the display will not be bogged down by large files. Large files other than images are also recognised so that you can visually see where the large files are. An icon image with BIG FILE is shown for easy detection.
- THUMBNAIL IMAGES:
Acceptable image files that the browser can load and scale are loaded and scaled to the thumbnail size.
- NON-IMAGE FILES:
Files that are not images--audio, anim, pic files that have no extension, etc. appear as empty unloadable boxes. HOWEVER THEY REMAIN CLICKABLE. If you have an external viewer configured for that file--audio player, animation palyer, etc.--then clicking the empty rectangle will result in your being able to hear, view, etc.
- HTML DOCS:
The exception to the above are HTML documents (web pages). It is useful to identify them as in a browser environment they are significant. If you click them, you see a web page. Thus a website directory can be browsed in a non-linear fashion by picking our various html pages in the display to click.
- FILENAME, FILESIZE, DATE
Most importantly, in addition to displaying all the files in one way or another, and making them all clickable, name, filesize, and date information is written below each image.
GENERATION OF THUMBNAIL HTML DOCS FOR ARCHIVES
WWWworkbench generates the directory displays into html documents (as Ram:T/W4/xx-PICS.HTML )which then the browser loads. Once loaded these files are deleted because they will be available on the browser screen or cache. If you want to create indexes for archives, first create the archives, then open up a WWWworkbench window for the archive drawer, and then save the on-screen display via 'save source'
DIRECTORY MANAGEMENT AND EDITING
Each display provides a number of menu items that trigger AmigaDos commands -- Delete -- CopyTo -- MoveTo -- Rename -- Clone -- MakeDir -- DelDir (delete directory). The system is designed so that you select the desired file from the file requester. Multiple selection is achieved through the Selection List which even allows files to be selected across many directories. Note the destination directory for copy and move are another open window, which you can select. Prompts will help you understand how it works, so there is no need to cover all the details here. As mentioned above, if you select a single filethumbnail (and if teh selectionlist is CLEAR) no selectionlist will appear. You can select a menu action at it will be performed on that selection. If more than one file is selected, the selectionlist becomes active.
NAVIGATION NOTES
- BIG DRAWER ICONS
These represent drawers (directories) found within the displayed directory. If you select them, you can operate on them the same as files. If you double click them, a new WWWworkbench window will be opened on this drawer.
- TOP WINDOW-RELATED BUTTONS
- SL means Selection List. If the Selection List is closed, this button will open it.
- TOP DRAWER ICON--this drawer always brings up a file requester. It allows you to jump to a completely different directory (as opposed to cimbing up and down a local hierarchy)
- PARENT--creates a NEW window contining the parent directory. Note you may often have it in a window underneath so only need to click it forward
- REFRESH--menu operations will automaticlaly refresh only the window where the menu was clicked. If operations were performed on files of other windows, you can click REFRESH to cause a reloading of that window, to refresh it.
- CLONE--when clicked, a new window will be created AND it will be filled with the SAME contents as that of its parent. It may be useful if you are creating some sort of operation between files of the same directory.
MENU OPERATIONS
The most powerful addition to this version of WWworkbench is that it is possible to compile an action list of files. The list does not appear when you click only one image, for speed convenience. It only appears when you click on two files in a row. NOTE: the delay between two clicks is 2 seconds. So if you click the same file more than two seconds appart you will enter that file twice into the selection list. if you click it twice quickly, you will enter the View mode, and NOTHING IS ADDED TO THE SELECTION LIST. Note that !! the selection list pictures are links. If you click them they will dissappear. THUS YOU HAVE THE POWER TO EDIT YOUR LIST and don't have to start over again.
- MULTISELECT WINDOW
As just mentioned, selecting more than one file brings up the menu selection list window. . You can click many files in many windows to build the selection list. When done, clicking ANY menu in any window will cause sequential action of the entire contents. VERY convenient batch-processing! If the operation alters or deletes files or drawers, then windows need to be refreshed. Where needed, the scripts attempt to refresh affected windows after operations are done. Note that the refresh system is not perfect. If you select from a window and then close it, and then open the same directory again in a new window, WWWworkbench will not refresh the new window, but determine that the affected window has dissappeared. If at any time a window that you know has changed has not changed, just hit REFRESH on that window. Normally people do not have lots of directories open. In fact, it is good practice if you are selecting files from across many directories, to close the window after the selection. The menu selection list DOES NOT require the window of the selected file to remain open!!! This makes it possible to make selections from dozens of directories, closing the ones you are done with, and in the end having only one--just to access a menu.
- DESELECTION
To make the menu selection list fit real-world needs even better, I made it possible to DE-SELECT images. You will notice that if you click any image in the meu selection list, it will dissappear!
- CLEAR
Deselection only flags the items you do not want. For a complete housecleaning, use CLEAR. Many menu operations run CLEAR at the end anyway to clean things up for the next round. But you can clear it manually by clicking CLEAR. What this does is it removes everything pertaining to the selection list for an absolutely fresh start. It helps avoid some unforeseen buggy behaviour when a complete housecleaning is done now and then.
- VARIOUS MENU OPERATIONS
Most of the menu operations on files are those most commonly used for editing and managing directories. No need to cover them all here. The way each operates will quickly become self-evident. Requesters will appear in respect to crutial questions like do you REALLY want to delete, etc.
IN addition, custom operations on the images is provided by the button that allows you to select an arexx script. See the next section.
SPECIAL AREXX BUTTON
This button is designed for you to select a special arexx script which will act on files. Clicking on this button will not only bring up the requester to select the arexx script, but it will also prepare the filenames of the selected files for easy introduction into the selected arexx script and software it will run on. The filenames will be placed into the cliplist as file.i ( ie as file.1, file.2, file.3, etc.). Note you are not restricted to image files. Your list could be sound files and the program that will load them sequentially a sound-processing program with arexx support.
EDITING REMOTE WEBSITES VIA FTPMOUNT
Once you have provided WWWworkbench the paths to the remote website directory in terms of both the URL and the FTPMount: path, WWWworkbench will go to and load a remote directory just as if it is local. The only way you will know you are going to a remote directory are the FTPMount prompts which indicate what is happening with your FTP connection. Also, of course, things will happen much more slowly as everything has to travel through the phone lines.
WWWworkbench basically sends FTPMount standard Amigados commands. Its success in making the FTP editing actions on the remote directory is entirely dependent on the functioning of your FTPMount and the server being accessed. It is recommended you get FTPMount working on its own before having WWWworkbench incorporate it into its operations.
UNDERNEATH EVERYTHING IS PRETTY TAME
Unlike regular software which works pretty close to the ground, WWWworkbench is only a bunch of arexx scripts sending commands and recieving info. All that happens is that WWWworkbench processes script data, generates html documents and sends AmigaDos commands to FTPMount or local files, and sends the browser a surprisingly small number of commands. Thus the operation of WWWworkbench is very normal and tame underneath, even though the final effect may SEEM like a single new software program.. Also, since the program is not running all the time, but rather scripts are run and then stop, run and then stop, the concept of a crash is virtually absent. You may simply discover that one particular operation didn't work for some reason. (Let me know)
Registration, Legalities, etc.
SHAREWARE
Become a registered user and recieve any future cleaned up and fixed up version, plus more scripts and operations. WWWworkbench is offered according to the shareware concept. The price set is $10 US. For registration just send me a letter with payment and your information---MOST IMPORTANT YOUR EMAIL ADDRESS because that is the only way I will send you the material. Unfortunately transferring money internationally is complicated. Often it is easiest to put cash inside a regular-looking letter. I will accept any loss in the mail, if you insist you sent it. So just send the cash in a letter and email me if I fail to respond. I will probably accept your explanation. Send any currency as long as it's approximately correct. Questions? Ask me:email.
WWWworkbench is designed based on my real world experience, and it is not a toy, so you benefit from my knowedge of what is useful. Examples of websites of mine (click here and they will appear in this window--you have to expand the window to fill the screen)
an international resort
a medium size resort
my own website of wildlife paintings
SEND REGISTRATION LETTER TO:
Andres Pääbo
Box 478
Apsley, Ontario
CANADA, K0L 1A0
EMAIL
STANDARD LEGALITIES.....
- COPYRIGHT
Copyright 1998 me, at the above address. Since the WWWworkbench is not just one script but a systematic operation of scripts, copyright relates also to the overall system, and not just individual scripts. As mentioned, WWWworkbench does not merge in any abnormal way with the web browser or FTPMount. For all copyright, legal, etc issues relating to the browser you are using (or FTPMount if you are using it) please see their documentation.
- THE USUAL DISCLAIMER-
"This software is provided "as is" . No warranties are made, either expressed or implied, with respect to reliability, quality, performance, or operation of this software. The use of this program is at your own risk. The author of this software operation assume any responsibility or liability for any damage or
losses resulting from the use of this software, even if advised of the
possibility of such damage or loss. "
- LICENCE-SHAREWARE
Free use of WWWworkbench is limited to initial testing, experimenting. Once you decide you want to keep it to use again and again, you must legally get licenced by getting registered . See the 'SHAREWARE' section above.